home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
pc_board
/
uupcb100.zip
/
DBFSETUP.NEW
< prev
next >
Wrap
Text File
|
1992-04-18
|
7KB
|
154 lines
DBFSETUP History File
Version 0.78 - 4/18/92 This is a bug fix release. In some situations, Version
0.77 was causing QEMM Exception 13 errors. In addition
Flat File imports would terminate prematurely. Fixed.
Also cleaned up some problems with displays.
Version 0.77 - 4/6/92 Added two new features:
(1). Flat File import
(2). Report function now routes to LPT1:, LPT2: or
a file.
┌──────────────────────────────────────────────────────────────────────────┐
│NOTICE: THIS VERSION USES THE SAME FORMAT AS DBFSETUP 0.75 AND 0.76. IF │
│YOU ARE CURRENTLY RUNNING DBFSETUP VERSION 0.74 OR EARLIER, READ THE │
│UPGRADE INSTRUCTIONS FOR VERSION 0.75 BELOW. │
└──────────────────────────────────────────────────────────────────────────┘
┌────────────────┐
│Flat File Import│
└────────────────┘
This feature will allow you to add a large number of Usenet newsgroups to
your system quickly and with little hassle.
This function is intended to import segments of the UNIX "active" file,
which is the master listing of newsgroups found on a typical Unix Usenet
system.
An active file looks like this:
comp.os.msdos.apps 0000456 0000234 y
comp.dcom.telecom 0005780 0004567 m
These four entries are:
1. The newsgroup name (imported by DBFSETUP)
2. The high message pointer on the unix system.
3. The low message pointer on the unix system.
4. The letter "y" (lower case!) if not moderated, the letter "m" if
moderated.
You can fake an active file, if necessary, by substituting "0" for the
pointers. DBFSETUP ignores the pointers. It only looks at the first
and fourth entries on each line. Therefore, if you create an ascii file
with the names of the newsgroups you want to import, two dummy entries
and the y or m flags for moderator status. A dummy file might look like
this:
comp.os.msdos.apps 0 0 y
comp.dcom.telecom 0 0 m
Once you have your active file, edit it with a good text editor to
include ONLY those newsgroups you want. Then start DBFSETUP. Take the
"F" option (Flat File). DBFSETUP will ask you for the filename. If
that file is not found, DBFSETUP will report an error.
The next question is the PC Board Conference number to start with. For
example, 500. DBFSETUP will enter the first line of the active file in
conf 500, the next line in conf 501, and so on.
DBFSETUP will fill in fields # 1(PC Board Conf #), 2 (Usenet newsgroup),
3(moderated Y/N) and 4(Moderators email address). The moderators email
address utilizes the uunet alias service. With this service, email can
be sent to an alias address on uunet and it will be forwarded to the
moderator. You do *NOT* have to be a uunet subscriber to use this.
DBFSETUP will enter the address in the Moderators Email ID field. For
example, for the moderated group "comp.dcom.telecom", DBFSETUP will
automatically enter the ID: "comp-dcom-telecom@uunet.uu.net". You can
manually edit this later, if you wish.
┌─────────────────────┐
│Report Output Options│
└─────────────────────┘
When you select the "R" option, it will now give you three choices,
LPT1:, LPT2: and print to file. If you elect print to file, it will ask
you for the filename.
Version 0.76 - 4/5/92 Revised to take care of problems with the display
of record numbers. No other changes.
Version 0.75 - 4/4/92 This version is revised to support new fields.
┌───────────────────────────────────────────────────────────────────────────┐
│NOTICE: BEFORE RUNNING THIS VERSION OF DBFSETUP, YOU MUST CONVERT YOUR │
│DATABASE. RUN CONVDBF.EXE IN THE DIRECTORY THAT HOLDS UUPCB.DBF. THIS │
│WILL ADD THE FIELDS TO EACH DATABASE RECORD. YOU SHOULD REINDEX THE │
│UUPCB.DBF FILE AFTER CONVERSION. SEE CONVDBF.DOC FOR FULL INSTRUCTIONS. │
└───────────────────────────────────────────────────────────────────────────┘
The screen now looks like this:
┌─────────────────────────────────────────────────────────────────────────────┐
│ uuPCB DBF Setup - 0.75ß │
│ Copyright 1991, 1992 Edward T. Hopper - All Rights Reserved │
│ Ed Hopper's BBS 713-997-7575 or ed.hopper@ehbbs.hou.tx.us │
└─────────────────────────────────────────────────────────────────────────────┘
PC Board Conference Number: 1 Active Record 1 of 24
USENET Newsgroup : news.newusers.questions
Moderated Newsgroup? (Y/N): N
Moderators email address :
Host for articles (opt) :
Default Distribution (opt):
Conference Path : D:\PCB\TEST1\MSGS
Conference Name : U-NewQuest
Archive Directory : \
Archive Dir File : \
Archive Flag : > New Fields
Archive Prefix : /
Block Flag : /
─────────────────────────[Esc to Abort Edit or Entry]──────────────────────────
[A]dd [C]Names Import [D]elete [E]dit
[N]ext [P]revious [Q]uit
[R]eport [U]ndelete [#] Goto Record #
Your Choice:
Note that five new fields are added. These are the following:
Archive Directory - Directory in which to store archived messages.
Archive Dir File - PC Board style Directory File to hold descriptions.
Archive Flag - Numerical value fron 0 to 5 (default is 0).
Archive Prefix - 1 to 5 character prefix for files stored from this newsgroup.
Block Flag - if Y messages from this newsgroup will not be posted nor will they
go in the junk conference.
The functions associated with these fields are described in UUPCBIN.NEW.
No other changes are made to this version.
Version 0.74 - Experimental, not released.
Version 0.73 - 1/14/92- Plugged a lot of holes that lead to abnormal term-
inations. The problem came from situations in which
a DBF entry would have resulted in a duplicate key
in the index. This was an error situation, but it
was not being trapped. I have not been able to break
this version (but I am not as creative as some! :-))
Fixed the problem with improper carry over of
the conference path and name fields.
Fixed problem with improper display of Record #X of X
display.
Fixed CNAMES.@@@ import routine. It will now accept
the entry of the PATH only (with or without trailing
"\") or the PATH and FILENAME.
Version 0.72 - 1/10/92- Not generally released
Version 0.71 - 1/2/92 - Fixed problem with overflows in LARGE CNAMES.@@@
files. It was giving invalid paths, particularly
above conference 200 or so.
Version 0.70 - 1/1/92 - Initial Release